
There are two sets of files to replicate the empirical results of the paper: STATA files and GAUSS files. 
The STATA files provide the graphic outputs in *.gph files, and the GAUSS files provide the table outputs in *.txt files. 

Even if the user is unfamiliar with GAUSS, he/she can still obtain at least parts of the table outputs by running the STATA program: 
specifically, the estimates of the tables in the paper, and the t-values computed with the usual OLS asymptotic variance estimator, 
but not the confidence intervals (CI's) computed with bootstrap in the paper.  

The details of the STATA and GAUSS files are as follows.





========== STATA FILES DESCRIPTION==========


The enclosed STATA program "Election_26AUG2017_Stata.do" produces Table 1, all estimates in Tables 2 and 3, and Figures 2 and 3.
The *.log file is the saved result corresponding to the .do file and it includes Tables 1, 2, and 3. 
And the *.gph files are figure outputs also generated with the .do file. 


What the STATA program does not produce is the confidence intervals (CI) based on bootstrap in Tables 2 and 3; 
instead of the CI's, the STATA program provides the usual t-values based on the OLS asymptotic variance estimator for all OLS-based estimates. 
Because of this, the OLS CI's in the paper differ somewhat from those in the STATA output file.


The STATA program does not provide any t-value for the "boundary-weighting (BW)" estimator in Tables 2 and 3, 
because BW is a complicated estimator, not based on OLS.

If the reader desires to generate bootstrap CI's, he/she may use the bootstrap option for OLS provided by STATA.


In the STATA program, "mf" appears, which stands for "multiplicative factor" in selecting the bandwidth

   h=mf*SD(S)*N^(-1/6)   where S is the running variable in use.


The "mf" value is typically about 0.5-2.5, and it was already chosen with Cross-Validation (CV) using a GAUSS program.
The STATA file uses the pre-selected value of "mf" without redoing the CV procedure.


The reason for not providing the bootstrap CI's and not doing the CV procedure in the STATA program is that
these procedures require a sophisticated programming with STATA,
which the authors could not do, as they are not regular users of STATA. 





========== GAUSS FILES DESCRIPTION==========


For the GAUSS files, all files are written in GAUSS, which is a programming language from Aptech Systems Inc. 
GAUSS files can be opened with any text file editor (e.g., notepad or wordpad).
In our paper, empirical parts were done with GAUSS, except for Figures 2 and 3.


GAUSS is similar to Matlab and R, and if the reader is familiar with these, he/she should be able to learn GAUSS quickly. Aptech Systems provides 
a free trial version of GAUSS for 30 days. Aptech Systems also used to give out a student version of GAUSS, or ��GAUSS light��, free of charge. If 
the reader has any of these, our GAUSS programs will run fine also with these data-size-limiting versions, as our data size is small.

 
The standard errors in the empirical part of the paper were computed with bootstrap from 
"GAUSS_ChoiLee2017_Table2_CI_26AUG2017" and "GAUSS_ChoiLee2017_Table3_CI_26AUG2017".



"USelec_SenateRepre_final_noname.txt" is a text data file without variable labels, 
and this file includes the following variables in the order of their appearance:

congress : number of congress
year : year
totalseathouse : total number of seats in House
democrats_h : number of Democrats in House
oppositions_h : number of Republicans in House
others_h : number of the others in House
propdemo_h : proportion of Democrats in House
totalseatsenate : total number of seats in Senate
democrats_s : number of Democrats in Senate
oppositions_s : number of Republicans in Senate
others_s : number of the others in Senate
propdemo_s : proportion of Democrats in Senate
lpi : LPI score
mli : MLI score



The estimation results in Table 2 and 3 are obtained by running the following four GAUSS programs:

"GAUSS_ChoiLee2017_Table2_26AUG2017" : to obtain the estimation results in Table 2
"GAUSS_ChoiLee2017_Table3_26AUG2017" : to obtain the estimation results in Table 3
"GAUSS_ChoiLee2017_Table2_CI_26AUG2017" : to obtain the CI's in Table 2
"GAUSS_ChoiLee2017_Table3_CI_26AUG2017" : to obtain the CI's in Table 3



The GAUSS program "GAUSS_ChoiLee2017_CV_26AUG2017" provides CV results to choose 'mf' for the bandwidths used in the above four programs; 
'mf' stands for "multiplicative factor" in selecting the bandwidth

   h=mf*SD(S)*N^(-1/6)   where S is the running variable in use.


The chosen CV bandwidths were already used in the four programs, so that there is no need to run the CV program.



All files with ".txt" other than the data file are the saved results corresponding to the GAUSS programs. 
The CI's computed with bootstrap can differ a little from the bootstrap CI's in the paper due to the rather small sample sizes.



To run the GAUSS programs, the user need to specify the location where the data are saved, using "load ..." command as in 

"load dat[n,14]=c:\dataverse_files\USelec_SenateRepre_final_noname.txt;"

where "USelec_SenateRepre_final_noname.txt" is the data file in the location 
"c:\dataverse_files\Data_ChoiLee2017_PA_GAUSS".

That is, if the user saved the data file in "d:\mydata", then the above command line should become

"load dat[n,14]=d:\mydata\USelec_SenateRepre_final_noname.txt;"



When a GAUSS program is run, the output is directed to an output window, or "command input-output" window. 
To send the output to a file at the same time, "output file" command can be used as in

"output file=c:\dataverse_files\GAUSS_ChoiLee2017_CV_results.txt reset;"

where the output is stored in the file named "GAUSS_ChoiLee2017_CV_results.txt" at the location 
"c:\dataverse_files\Data_ChoiLee2017_PA_GAUSS".

That is, if the user desires the output to be saved in the file names "myoutput" in "d:\mydata", then the above command line should become

"output file=d:\mydata\myoutput reset".

In this command, "reset" means that each time the program is run, the old output, if there is any, is replaced by the new output. Instead, 

"output file=d:\mydata\myoutput on"

attaches the new output to the old output.



